Methods and apparatus to identify session users with cookie information

ABSTRACT

Methods and apparatus are disclosed to identify session users with cookie information. An example method includes identifying a most recently used cookie based on a comparison of timestamps associated with a plurality of cookies, comparing an identifier of the most recently used cookie to a cookie table, the cookie table associating cookies with the plurality of different users, and when the identifier of the most recently used cookie is associated with one of the plurality of different users, associating subsequent usage activity of the computing device with the one of the plurality of different users.

RELATED APPLICATION

This patent arises from a continuation of U.S. patent application Ser.No. 14/641,982, filed on Mar. 9, 2015, issued as U.S. Pat. No.9,232,014, on Jan. 5, 2015, which is a continuation of U.S. patentapplication Ser. No. 13/396,071, filed on Feb. 14, 2012, issued as U.S.Pat. No. 9,015,255, on Apr. 21, 2015, both U.S. patent application Ser.No. 14/641,982 and U.S. patent application Ser. No. 13/396,071 arehereby incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

This disclosure relates generally to audience measurement, and, moreparticularly, to methods and apparatus to identify session users withcookie information.

BACKGROUND

Establishment of demographically selected household panelists allowsmarket researchers an opportunity to collect behavior data of anaudience and to project the occurrence of one or more such behaviors toa larger population. Household panelist data allows statisticallysignificant projections that correspond to various types of consumerbehavior including, but not limited to television exposure behavior,shopping behavior, Internet browsing behaviors, and/or behavior relatedto computing device interaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an example computing deviceconstructed in accordance with the teachings of this disclosure toidentify session users with cookie information.

FIG. 2 is a schematic illustration of an example implementation of thecookie user identifier of FIG. 1.

FIG. 3 is an example table generated by the example cookie useridentifier of FIG. 2.

FIGS. 4 and 5 are flowcharts representative of example machine readableinstructions which may be executed to identify session users with cookieinformation.

FIG. 6 is a block diagram of an example system that may execute theexample machine readable instructions of FIGS. 4 and 5 to implement theexample cookie user identifier of FIGS. 1 and 2, and/or to build theexample table of FIG. 3.

DETAILED DESCRIPTION

Methods and apparatus are disclosed to identify session users withcookie information. An example method includes identifying activityassociated with a first cookie having a first type, in response toidentifying the first, parsing the first cookie to identify a firstpanelist, when the first cookie includes an identifier associated with afirst panelist, associating current usage activity of the computingdevice with the first panelist, and when the first cookie includes anidentifier unassociated with the first panelist, associating currentusage activity of the computing device with a guest

Audience measurement companies enlist persons and/or groups of persons(e.g., households) as panelists. To become a panelist, such personstypically undergo a registration process in which they provide theirdemographic information to the audience measurement company. Often, theaudience measurement entity will assign an identifier to the person toenable collected data to be mapped to the demographics of the panelistcorresponding to the user. The audience measurement company willtypically also provide the panelist with one or more software and/orhardware metering devices to collect media exposure data. The precisetype(s) of metering device(s) may vary depending on one or more of thetype of information being collected, the type of device(s) beingmonitored, the environment(s) in which the panelist is to be monitored,and/or the type(s) of media (e.g., radio, television, Internet, etc)exposure and/or behavior(s) to be monitored. In some applications, thepanelist is provided with a first meter to identify the members of anaudience (e.g., a people meter) and a second meter to collect dataidentifying or enabling identification of the media to which thepanelist is exposed. The audience measurement company may deliver and/orinstall such meters in the panelist's home and/or on the panelist'smedia delivery equipment (e.g., computer, television, set top box, etc).Alternatively, the panelist may be provided with the metering softwareand/or hardware via an automated installation (e.g., via a download overthe Internet) and/or the panelist may be asked to perform some or all ofthe installation.

During a study, panelists may receive reminders and/or prompts toidentify themselves. In some examples, a panelist that agrees to havetheir television behavior monitored is provided buttons or other inputs(sometimes referred to as a people meter) that allows the viewer toselect their name in response to a prompt to self-identify. Viewinginformation, such as current channel, current time and/or viewingduration of the viewer is associated with the household individualidentified via the metering device (e.g., a PeopleMeter deviceassociated with The Nielsen Company®).

In other examples, panelists may agree to allow their computing devicebehavior to be monitored. Computing device monitoring may includecollecting data reflecting browsing behavior, access to Internetresources, purchasing of products, etc., to enable analysis of on-lineconsumer behavior, trend development, advertising effectivenessassessment, brand advocacy assessment, and/or social media buzz tobetter understand how consumers engage with various online media.Panelist households may include one or more computing devices, such asdesktop personal computers, laptops, netbooks, personal digitalassistants, mobile phones and/or tablets (e.g., iPADs). The computingdevice(s) may be centrally located and/or otherwise located in one ormore areas of the household that result in shared use between householdmembers. A panelist and/or a household of panelists (e.g., familymembers, roommates, etc.) that agree to have their computing deviceusage monitored may be presented with an on-screen prompt to identifywhich user is interacting with the computing device. However,participation by panelists may be discouraged and/or reduced when one ormore techniques to prompt for identification become burdensome and/orare perceived to be invasive.

Even when a household panelist provides an indication of their identityprior to using a household computing device (e.g., by selecting theirname on an on-screen prompt), the panelist may leave the computingdevice and a different household user (e.g., another panelist of thesame household) may begin to use it without providing any indication ofthe change in users. In such example circumstances, logging informationabout computer usage behavior (e.g., web sites visited, on-linepurchasing, bill payment activity, etc.) results in one or moreinaccurate datasets as the activity is attributed to the wrong panelist.For example, if household panelist “John” responds to an on-screenidentification prompt of a shared computing device (e.g., an AppleiPad®) located in the household, then subsequent usage of that computingdevice is recorded (e.g., by a monitoring program operating on thecomputing device), and forwarded to a monitoring organization (e.g., TheNielsen Company®) as associated with the household panelist “John.” Johnhas a particular demographic profile (e.g., age, income, etc.). In theevent another user (which may or may not be a household panelist)subsequently begins using the computing device after John withoutanother logon event identifying the user change, then the subsequentlyrecorded behavior will be skewed and/or otherwise erroneous if thesecond panelist has different demographic characteristics than the firstuser, John (e.g., a different age, a different gender, a differentincome, etc.).

Example methods, apparatus, systems and/or articles of manufacturedisclosed herein passively identify a current user of a computing devicein an environment where more than one individual is expected to use thesame computing device. Activities typically performed by users ofcomputing devices include checking social networking status informationand/or checking for the presence of electronic mail (e-mail) messages.Web-based e-mail and/or social networking services often use cookies(e.g., a numeric and/or alphanumeric identifier) to identify users. Eachcookie is unique to a particular user of the service. Additionally, thecookies employed by such web-based services may persist on the computingdevice (e.g., in the cache, on the hard drive, etc.) after a user closes(e.g., shuts-down) a browser and/or turns off the computing device. As aresult, when the user re-opens their web browser and navigates to a webaddress (e.g., a uniform resource locator (URL) associated with the webservice, such as www.facebook.com), the web service may still access apersistent cookie to allow the web service to configure its services ina manner that tailors to one or more preferences of the user, and/or toallow the user to access the web service without manually enteringauthentication credentials again.

Participation with social networking services and/or e-mail services isa computing device activity associated with relatively high reach whencompared to other computing device activities (e.g., gaming). Forexample, sixty to seventy percent of computing device sessions in theU.S. are believed to include access to the social networking servicenamed Facebook®. Example methods, apparatus, systems and/or articles ofmanufacture disclosed herein access cookies stored on and/or transferredby a computing device to determine an identity of the current user in anon-invasive manner (i.e., without requiring another prompt of theuser).

FIG. 1 is a schematic illustration of an example computing device 100that may be used by any number of household panelists. In theillustrated example of FIG. 1, the computing device 100 includes a firstbrowser (“Browser A”) 102, a second browser (“Browser B”) 104, and athird browser 106 (“Browser C”) 106. Each of the example first, secondand third browsers (102, 104, 106) may be designed and/or otherwisedeveloped by different entities that distribute browsers. Examplebrowsers include, but are not limited to, Microsoft® Internet Explorer®,Mozilla Firefox®, Apple® Safari®, Android®, Google® Chrome® and Opera®.

The example computing device 100 of FIG. 1 includes a platform memory108, such as a hard drive, a solid state memory and/or any other type ofmemory. The platform memory 108 is able to store cookies received viaany of the first, second and third example browsers (102, 104, 106).Each web browser stores cookies from user sessions in a unique directoryof the platform memory 108. Cookies are not shared and/or otherwiseviewed by foreign browsers. In other words, each browser manages andviews only those cookies that result from their corresponding websessions. In the illustrated example of FIG. 1, the platform memory 108includes a first browser cookie directory 110, a second browser cookiedirectory 112 and a third browser cookie directory 114 to store cookiesfor each of the first, second and third browsers (102, 104, 106),respectively. Each of the first, second and third browsers (102, 104,106) are communicatively connected (e.g., via a wired or wirelessconnection) to an example network interface 116 to facilitatecommunication to one or more network(s) 118, such as one or moreintranets and/or the Internet.

Panelists that agree to have their computing device behavior monitoredmay also agree to have one or more monitoring devices and/or programsinstalled on their computing devices. In the illustrated example of FIG.1, the computing device 100 includes a panelist monitoring agent 120 tomonitor and record interaction between household panelists and thecomputing device 100. While the illustrated example of FIG. 1 showspanelist monitoring techniques by way of the panelist monitoring agent120 (e.g., a software-based monitoring program executed by a processorof the computing device 100), the techniques to monitor user behaviorare not limited thereto. For instance, in some examples, the panelisthousehold may be monitored via one or more routers of the household toidentify what websites are visited and/or websites may be tagged withmonitoring instructions that cause the browser 102, 104, 106 to send amessage (e.g., an HTML request) to the audience measurement entity toenable the audience measurement entity to log the access to the webpage. As described in further detail below, the example computing device100 of FIG. 1 also includes an example cookie user identifier 122 tofacilitate identification of users with cookie information.

FIG. 2 is a schematic illustration of an example implementation of thecookie user identifier 122 of FIG. 1. In the illustrated example of FIG.2, the cookie user identifier 122 includes a platform analyzer 202, anapplication storage interface 204, a persistent cookie manager 206, aduplicate identifier 208, a cookie temporal analyzer 210, an activityassociator 212, a timer 214 and a persistent cookie change monitor 216.In operation, the example platform analyzer 202 scans and/or otherwisesearches the computing device 100 for programs and/or applicationsassociated with browsing functionality. In some examples, the platformanalyzer 202 may search a registry and/or program listing of thecomputing device 100 for particular installed programs and/orapplications. The example persistent cookie manager 206 invokes theexample application storage interface 204 to identify a persistentcookie stored in the example platform memory 108. For each browserprogram and/or browser application identified by the example platformanalyzer 202, the example application storage interface 204 locatescorresponding storage location(s) of cookies for that browser.

In some examples, the persistent cookie manager 206 identifies theselocations by searching for cookie directories in the platform memory. Inthe illustrated example, the application storage interface identifiesthe first browser cookie directory 110, the second browser cookiedirectory 112 and/or the third browser cookie directory 114 to searchfor one or more types of cookies. The application storage interface 204looks for known cookie tag formats. Web services often employ cookie tagnomenclature that is indicative of a particular web service. Forexample, the cookie tag “c_user” is associated with Facebook®. If aknown web service cookie tag is identified by the example persistentcookie manager 206, then an associated panelist user identity isidentified, if any. For example, the first time a panelist participateswith one or more known web services, the monitoring entity may cultivateinformation associated with the current user to associate the panelistand/or panelist information with the known web service. At the initialtime of association between the current user (current panelist) and theweb-service, unique identifiers are associated with the panelist, suchas the unique “c_user” cookie identifier for each user of the Facebook®web-service. While the illustrated examples disclosed herein include thec_user cookie tag employed by Facebook®, example methods, apparatus,systems and/or articles of manufacture disclosed herein are not limitedthereto. For example, other web services may employ additional and/oralternate cookie tags that operate in a similar manner as the c_usercookie tag.

The c_user cookie tag employed by Facebook® includes an associatednumeric value that is unique to each user of the Facebook® web services.Each time a Facebook® user logs on to a computing device for any browsertype, the c_user cookie tag is populated with an identifier unique tothat user. If the user explicitly logs-off from the Facebook® website(e.g., by clicking a “log-off” icon from the Facebook® interface), thenthe c_user cookie and its corresponding identification information isdestroyed and/or otherwise removed from the computing device. In theevent the user logs onto the Facebook® web services using an alternatebrowser and/or a different computing device, the same identificationvalue is populated with the c_user cookie tag on that alternate browserand/or different computing device. However, if the user closes thebrowser without explicitly logging off from the Facebook® interface,then the c_user cookie and its corresponding identification informationpersist on the computing device. In particular, the c_user cookieremains stored in the particular memory location of the example platformmemory 108 location associated with the browser that was used by thatuser to obtain the cookie.

If a second user of the example computing device 100 logs onto Facebook®using the same browser that was used by the prior Facebook® user, thenthe previously stored c_user cookie is replaced with informationassociated with the second user (e.g., in the first browser cookiedirectory 110). However, when the second user of the example computingdevice 100 logs onto Facebook® using an alternate browser, then a newc_user cookie is stored in the memory directory associated with thealternate browser (e.g., the second browser cookie directory 112), andthe previously stored c_user cookie associated with the previously usedbrowser (e.g., the first browser cookie directory 110) is unaffected.

The example cookie manager 206 of FIG. 2 generates, updates and/orotherwise manages a cookie table to track associations between cookiesand household panelists. Turning to FIG. 3, a cookie table 300 includesa household user column 302, a cookie domain column 304, and a serviceidentifier (ID) column 306. For each household member (e.g., members“John,” “Jan,” and “Mary”) a corresponding cookie domain and service IDis listed for web services used by the household member. In theillustrated example, each of the web-based services uses one or morecookie tag(s) having a nomenclature unique to that service. For example,Facebook® uses a cookie tag labeled “c_user,” while other web-basedservices may employ any other names for their associated cookie(s).Known cookie tag nomenclature may be stored in the example cookiedatabase 207 to facilitate queries and/or look-up operations of cookiesstored in the example platform memory 108 by one or more browsers. Tostay current with additional and/or alternate cookies and/orcorresponding cookie tag nomenclature, the example cookie useridentifier 122 may access one or more server(s) via the example networkinterface 116 to access information related to web-based services and/orcorresponding tag nomenclature.

In the illustrated example of FIG. 3, panelist members John and Maryeach participate with Facebook®, an e-mail service, and a second socialweb-based service labeled “Social #2” (e.g., Twitter®, Blogster®,deviantART®, Epernicus®, Flickr®, Foursquare®, Google+®, etc.). On theother hand, Jan only participates in a web-based service associated withan e-mail service provider. In the event that Jan joins one or moreadditional and/or alternate web-based services in the future, theexample cookie manager 206 will add additional row(s) of informationthereto. In the example of FIG. 3, household user John, for example, ispresently associated with a Facebook® cookie (e.g., as evidenced by thecookie nomenclature “c_user”) and a corresponding service identifier“4145426609.” In the example of FIG. 3, household user John is alsopresently associated with an e-mail service (e.g., as evidenced by thecookie nomenclature “xyz”) and a corresponding service identifier“3239533200,” and is associated with another social networking service(e.g., as evidenced by the cookie nomenclature “tuv”) and acorresponding service identifier “9205697500.” In the example of FIG. 3,example household user Mary is also associated with a Facebook® cookie(e.g., as evidenced by the cookie nomenclature “c_user”) and acorresponding service identifier “4932915678.”

As described above, security mechanisms prevent one browser from havingaccess to the cookies associated with another browser. Additionally,security mechanisms prevent one web service (e.g., domain) from beingable to access cookies associated with another web service (e.g., asecond web service domain). However, the example panelist monitoringagent 120 has full access to the resources of the example computingdevice 100 by virtue of panelist consent and, thus, may access allcontent generated and/or otherwise stored by all browserprograms/applications that may operate on the example computing device100.

In the event that the cookie manager discovers a cookie associated withone of the household panelist members, the possibility exists that aseparate browser also has a cookie of the same type for the same user.For example, the user may have used a first browser to access Facebook®at a first time, but may have more recently used a second browser on thecomputing device 100 at a second time to access Facebook®. As such, bothbrowsers will have a cookie of type c_user and the corresponding userservice identifier. To identify which cookie is the most recentlycreated and/or otherwise modified, the example duplicate identifier 208invokes the example application storage interface 204 to search forother cookies that use the “c_user” nomenclature. Additionally, theexample cookie temporal analyzer 210 compares cookies to determine whichone is most recent (e.g., via a creation timestamp, via a modificationtimestamp, etc.).

In some examples, a first user (panelist) of the example computingdevice 100 logs onto a website that provides cookies such as Facebook®and, some time later, walks away from the computing device 100 withoutlogging out. As described above, the cookie tag of type “c_user” isdeleted from a browser cookie storage when a user explicitly selects alog-out option from the (e.g., Facebook®) interface. If a second user(panelist) of the example computing device 100 logs into the samewebsite (e.g., Facebook®) using the same browser that had been used bythe first user, then the cookie tag of type “c_user” is replaced withthe service identifier associated with the second user. On the otherhand, if the second user of the example computing device 100 logs intothe webpage (e.g., Facebook®) using a different browser than the oneused by the first user, then the cookie tag of type “c_user” for thefirst browser remains in the platform memory 108, and a new cookie tagof type “c_user” for the second browser is created and stored in theplatform memory 108.

To determine which user is likely the current user, the example cookiemanager 206 identifies both cookie tags of type “c_user,” and invokesthe example cookie temporal analyzer 210 to determine which one is morerecent. When the most recent user is identified, based on thecorresponding service identifier associated with the most recent cookie,the example activity associator 212 associates subsequent behavior onthe platform 100 with the most recent user.

In other examples, a first user of the computing device 100 (e.g., John)may log into a web-based service, such as Facebook®, and leave thecomputing device 100 without logging out. If a second user begins to usethe computing device 100 and logs into any other website (e.g., the sameor different type of web-based service) that uses cookies, then thecookie associated with the first user remains stored on the exampleplatform memory 108. For example, the second user (e.g., Mary) may logon to her e-mail account (e.g., having a cookie tag nomenclature “xyz”)using the same, or a different browser. As such, the example platformmemory has one cookie of a type associated with John's Facebook®account, and another cookie of a type associated with Mary's e-mailaccount. The example cookie temporal analyzer 210 determines which ofthe two (or more) cookies is more recent and associates the user of themore recent cookie with current usage of the computing platform 100.

While an example manner of implementing the cookie user identifier 122of FIG. 1 has been illustrated in FIGS. 2 and 3, one or more of theelements, processes and/or devices illustrated in FIGS. 1-3 may becombined, divided, re-arranged, omitted, eliminated and/or implementedin any other way. Further, the example first browser 102, the examplesecond browser 104, the example third browser, the example first browsercookie directory 110, the example second browser cookie directory 112,the example third browser cookie directory 114, the example cookie useridentifier 122, the example platform analyzer 202, the exampleapplication storage interface 204, the example cookie manager 206, theexample cookie database 207, the example duplicate identifier 208, theexample cookie temporal analyzer 210, the example activity associator212, the example timer 214, the example cookie change monitor 216,and/or the example cookie table 300 of FIGS. 1-3 may be implemented byhardware, software, firmware and/or any combination of hardware,software and/or firmware. Thus, for example, any of the example firstbrowser 102, the example second browser 104, the example third browser,the example first browser cookie directory 110, the example secondbrowser cookie directory 112, the example third browser cookie directory114, the example cookie user identifier 122, the example platformanalyzer 202, the example application storage interface 204, the examplecookie manager 206, the example cookie database 207, the exampleduplicate identifier 208, the example cookie temporal analyzer 210, theexample activity associator 212, the example timer 214, the examplecookie change monitor 216, and/or the example cookie table 300 could beimplemented by one or more circuit(s), programmable processor(s),application specific integrated circuit(s) (ASIC(s)), programmable logicdevice(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)),etc. When any of the apparatus or system claims of this patent are readto cover a purely software and/or firmware implementation, at least oneof the example first browser 102, the example second browser 104, theexample third browser, the example first browser cookie directory 110,the example second browser cookie directory 112, the example thirdbrowser cookie directory 114, the example cookie user identifier 122,the example platform analyzer 202, the example application storageinterface 204, the example cookie manager 206, the example cookiedatabase 207, the example duplicate identifier 208, the example cookietemporal analyzer 210, the example activity associator 212, the exampletimer 214, the example cookie change monitor 216, and/or the examplecookie table 300 are hereby expressly defined to include a tangiblecomputer readable medium such as a memory, DVD, CD, Blu-ray, etc.storing the software and/or firmware. Further still, the example cookieuser identifier 122 of FIGS. 1 and 2 may include one or more elements,processes and/or devices in addition to, or instead of, thoseillustrated in FIGS. 1-3, and/or may include more than one of any or allof the illustrated elements, processes and devices.

A flowchart representative of example machine readable instructions forimplementing the cookie user identifier 122 of FIGS. 1 and 2 is shown inFIG. 4. A flowchart indicative of example machine readable instructionsfor identifying session users with cookies is further shown in FIG. 5.In these examples, the machine readable instructions comprise a programfor execution by a processor such as the processor 612 shown in theexample computer 600 discussed below in connection with FIG. 6. Theprogram may be embodied in software stored on a tangible computerreadable medium such as a CD-ROM, a floppy disk, a hard drive, a digitalversatile disk (DVD), a Blu-ray disk, or a memory associated with theprocessor 612, but the entire program and/or parts thereof couldalternatively be executed by a device other than the processor 612and/or embodied in firmware or dedicated hardware. Further, although theexample program is described with reference to the flowchartsillustrated in FIGS. 4 and 5, many other methods of implementing theexample cookie user identifier 122 may alternatively be used. Forexample, the order of execution of the blocks may be changed, and/orsome of the blocks described may be changed, eliminated, or combined.

As mentioned above, the example processes of FIGS. 4 and 5 may beimplemented using coded instructions (e.g., computer readableinstructions) stored on a tangible computer readable medium such as ahard disk drive, a flash memory, a read-only memory (ROM), a compactdisk (CD), a digital versatile disk (DVD), a cache, a random-accessmemory (RAM) and/or any other storage media in which information isstored for any duration (e.g., for extended time periods, permanently,brief instances, for temporarily buffering, and/or for caching of theinformation). As used herein, the term tangible computer readable mediumis expressly defined to include any type of computer readable storageand to exclude propagating signals. Additionally or alternatively, theexample processes of FIGS. 4 and 5 may be implemented using codedinstructions (e.g., computer readable instructions) stored on anon-transitory computer readable medium such as a hard disk drive, aflash memory, a read-only memory, a compact disk, a digital versatiledisk, a cache, a random-access memory and/or any other storage media inwhich information is stored for any duration (e.g., for extended timeperiods, permanently, brief instances, for temporarily buffering, and/orfor caching of the information). As used herein, the term non-transitorycomputer readable medium is expressly defined to include any type ofcomputer readable medium and to exclude propagating signals. As usedherein, when the phrase “at least” is used as the transition term in apreamble of a claim, it is open-ended in the same manner as the term“comprising” is open ended. Thus, a claim using “at least” as thetransition term in its preamble may include elements in addition tothose expressly recited in the claim.

The program 400 of FIG. 4 begins at block 402, in which the exampleplatform analyzer 202 searches the example computing device 100 forbrowser programs and/or applications. For example, a personal computerand/or laptop may use Google® Chrome®, Microsoft® Internet Explorer®and/or Mozilla Firefox®. In other examples, an Apple®-based product mayuse the Safari® browser. In still other examples, a wireless telephonemay use an Android® browser, Opera®, Dolphin®, etc. The example platformanalyzer 202 may locate one or more browser programs/applications bysearching a program library, a file structure and/or by analyzing anoperating system registry. For each browser program/applicationidentified by the example platform analyzer 202, the example applicationstorage interface 204 identifies one or more storage locationsassociated with and/or otherwise used by each browserprogram/application (block 404).

The example cookie manager invokes the example application storageinterface 204 to search the platform memory 108 of the platform andidentify a cookie of a first type (block 406). For example, becauseFacebook® web services reflect a relatively large portion of sessionactivity during computing device session(s), a search for cookies havingthe “c_user” tag may be assigned a high priority (e.g., preferredfirst). In some examples, the example cookie manager may direct theapplication storage interface 204 to search the platform memory 108 forone or more additional or alternate cookie tag nomenclature(s). If theexample cookie manager 206 identifies a cookie of a known type (block406), it determines an associated user identity via a lookup of theexample service ID column 306 of the cookie table 300 (block 408). Theidentified user is associated with a candidate user of the computingdevice 100. However, the possibility exists that the identified userinvokes more than one browser to gain access to the web serviceassociated with the persistent cookie. As such, the cookie identifiedmight not be the most recently generated cookie on the computing device100. To determine whether the identified cookie associated with thecandidate user is the most current, the duplicate identifier 208 invokesthe storage interface 204 to search memory locations associated with oneor more other browsers/apps that may be installed on the computingdevice 100 (block 410).

If a duplicate is found (block 412), then the cookie temporal analyzer210 identifies which cookie is most recent (block 414). The examplecookie temporal analyzer 210 may locate a timestamp of the cookies, adate of creation indicator of the cookies, and/or a date of modificationof the cookies to determine which cookie associated with the candidateuser is most recent. The most recent cookie and corresponding user isassociated with the candidate user of the computing device 100 (block414).

In some examples, a second user may use the computing device 100 toutilize the same web-based service as a prior user, but the web-basedservice may have been accessed via a separate browser program/app thanthe first user. To make sure that a second user (e.g., a user differentfrom the previously identified candidate user) is not the true candidateuser, the example cookie manager 206 searches for the same cookie type(e.g., a cookie using a “c_user” tag) associated with other user(s) inmemory locations associated with other browser programs/apps that may beinstalled on the computing device 100 (block 416). If a second(alternate) user associated with the same cookie type is identified(block 418), the example cookie temporal analyzer 210 determines whichcookie is more recent (block 420). If the second cookie is more recent(block 420), then the household user associated with the alternateservice ID is associated with the candidate user, effectively replacingthe previously determined candidate user (block 422).

On the other hand, if the second (alternate) user associated with thesame cookie type is not more recent (block 420) (e.g., as determined byan indication from a modification date, a creation date and/or othertimestamp), then the example application storage interface 204 searchesthe platform memory 108 for a cookie of an alternate type (block 424).For example, a separate web-based service may have been accessed by ahousehold member of the computing device 100 that is more recent, suchas a different social website, an e-mail website, a banking website,etc. If a separate cookie of an alternate type is identified that ismore recent (block 426), then the example program 400 of FIG. 4 returnsto block 408 to identify the corresponding user associated with the morerecent cookie. On the other hand, if the example computing device 100does not have any more cookies of alternate type(s) that are more recent(block 426), then the example activity associator 212 associates allbrowsing activity with the currently identified user (block 428).

In other examples, a current user of the example computing device 100may walk away, and a different user may begin using the computing device100. Additionally, because the prior user may not have logged off one ormore web-based services that employ cookies, the example timer 214manages a timeout period (block 430). If the timeout period does notoccur, then the example activity associator continues to associatecurrent activity on the computing device 100 with the currentlyidentified user. On the other hand, when the timeout period expires(block 430), then the program 400 returns to block 406 to search theplatform memory 108 again for one or more other cookies that may resultfrom one or more other web-based services invoked by the same (current)user, or a different user of the panelist household.

FIG. 5 is a flowchart representative of an example program 500 which maybe executed to identify session users with cookie information. Theprogram 500 of FIG. 5 begins at block 502, in which the activityassociator 212 determines whether a current user of the computing device100 has been identified. For example, a user (panelist) may haveexplicitly identified himself or herself before or during use of thecomputing device 100 via a PeopleMeter®, a dialog prompt and/or otherresponse to an identification request. The PeopleMeter® may, forexample, contain an array of selectable buttons or other user interfaceto allow a household member to indicate their identity prior or duringuse of the computing device 100. In response to receiving an indicationof a household user (block 502), the example activity associator 212attributes current activity with the computing device 100 to thecurrently identified user (block 504). The example cookie useridentifier 122 invokes the example cookie change monitor 216 to monitorfor any changes to known cookie types that may be stored on the platformmemory 108, such as cookies stored in the example first browser cookiedirectory 110, the example second browser cookie directory 112, and/orthe example third browser cookie directory 114 (block 506). Changes toone or more known cookie types (e.g., cookies having a tag nomenclature“c_user”) may include, but are not limited to added cookies, deletedcookies, cookie timestamp changes, cookie field value changes, etc.Additionally, such changes may occur in association with any of thebrowser applications/programs installed and/or otherwise executing onthe example computing platform 100. As described above, monitoringcookie change activity with respect to any browser application/programof the computing device 100 facilitates detection of some householdusers accessing web-based services on a first browser, while otherhousehold members utilize the same web-based services via anotherbrowser. In such example circumstances, both cookies may besimultaneously resident on the platform memory 108.

In the illustrated example of FIG. 5, if the cookie change monitor 216does not identify changes to one or more known cookie types (block 508),then the program 500 waits. Otherwise, in response to the example cookiechange monitor 216 detecting change(s) to one or more known cookie types(block 508), the example cookie manager 206 determines whether a changeto a known cookie type is associated with the currently identifiedhousehold panelist member (block 510). In some examples, the cookiemanager 206 parses and/or otherwise examines the content(s) of cookiesstored in the platform memory 108 for an indication of a panelistmember, such as a panelist username, a numeric value associated uniquelywith the panelist, and/or an alphanumeric value associated uniquely withthe panelist. As described above, the example cookie table 300 includesa service ID column 306 for each respective household member. If aservice ID value associated with a household member is detected by theexample cookie manager 206, then control returns to block 508 where theexample cookie change monitor 216 continues to monitor for changes tocookies stored on the platform memory 108. For example, the current userof the computing device 100 may have just accessed a social website(e.g., Twitter®) or an e-mail account (e.g., Google®).

On the other hand, if cookie activity is detected by the example cookiechange monitor 216 (block 508), and the changes are not affiliated withthe currently identified user (block 510), then the cookie manager 206queries the cookie table 300 to find a match (block 512). In the event acurrent household member cannot be identified via a match in the exampleservice ID column 306 of the cookie table 300 (block 514) (e.g., whenthe cookie is devoid of an indication of one or more panelistmember(s)), then a guest may be using the computing device 100. Forexample, one or more of the household panelist members may have one ormore guests in their home that wish to check their e-mail account(s)and/or check their social networking status(es). As such, the exampleactivity associator 212 identifies the current user as “none” (orsimilar) (block 516), and refrains and/or otherwise stops loggingactivity of the computer platform 100 with one or more householdmember(s) (block 518). Control then returns to block 508, where theexample cookie change monitor 216 monitors the example platform memory108 for changes to one or more cookies.

In the event that the example cookie change monitor 216 identifieschange activity (block 508), determines such cookie activity is notassociated with the currently identified user (block 510) (e.g., a userthat previously indicated their identity via a PeopleMeter® buttonpress), and identifies that the cookie change is associated with adifferent household panelist member (block 514), then the exampleactivity associator 212 associates the current activity with the otherhousehold panelist member (block 520). For example, the other householdpanelist member may be identified based on matching information from theservice ID column 306 of the example cookie table 300. The exampleactivity associator 212 associates activity on the example computingdevice 100 with the newly identified household member (block 522).Control returns to block 508 to allow the example cookie change monitor216 to identify one or more changes to new and/or existing cookiesstored on the example platform memory 108.

FIG. 6 is a block diagram of an example computer 600 capable ofexecuting the instructions of FIGS. 4 and 5 to implement the cookie useridentifier 122 of FIGS. 1-3. The computer 600 can be, for example, aserver, a personal computer, a mobile phone (e.g., a cell phone), apersonal digital assistant (PDA), a television, an Internet appliance, agaming console, a set top box, or any other type of computing devicethat stores a cookie.

The system 600 of the instant example includes a processor 612. Forexample, the processor 612 can be implemented by one or moremicroprocessors or controllers from any desired family or manufacturer.

The processor 612 includes a local memory 613 (e.g., a cache) and is incommunication with a main memory including a volatile memory 614 and anon-volatile memory 616 via a bus 618. The volatile memory 614 may beimplemented by Synchronous Dynamic Random Access Memory (SDRAM), DynamicRandom Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM)and/or any other type of random access memory device. The non-volatilememory 616 may be implemented by flash memory and/or any other desiredtype of memory device. Access to the main memory 614, 616 is controlledby a memory controller.

The computer 600 also includes an interface circuit 620. The interfacecircuit 620 may be implemented by any type of interface standard, suchas an Ethernet interface, a universal serial bus (USB), and/or a PCIexpress interface.

One or more input devices 622 are connected to the interface circuit620. The input device(s) 622 permit a user to enter data and commandsinto the processor 612. The input device(s) can be implemented by, forexample, a keyboard, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system.

One or more output devices 624 are also connected to the interfacecircuit 620. The output devices 624 can be implemented, for example, bydisplay devices (e.g., a liquid crystal display, a cathode ray tubedisplay (CRT), a printer and/or speakers). The interface circuit 620,thus, typically includes a graphics driver card.

The interface circuit 620 also includes a communication device, such asa modem or network interface card to facilitate exchange of data withexternal computers via a network 626 (e.g., an Ethernet connection, adigital subscriber line (DSL), a telephone line, coaxial cable, acellular telephone system, etc.).

The computer 600 also includes one or more mass storage devices 628 forstoring software and data. Examples of such mass storage devices 628include floppy disk drives, hard drive disks, compact disk drives anddigital versatile disk (DVD) drives. The mass storage device 628 mayimplement the platform memory 108.

The coded instructions 632 of FIGS. 4 and 5 may be stored in the massstorage device 628, in the volatile memory 614, in the non-volatilememory 616, and/or on a removable storage medium such as a CD or DVD.

From the foregoing, it will be appreciated that disclosed examplemethods, systems, apparatus and articles of manufacture facilitateidentification of session users by using cookie information associatedwith web-services used by household panelist members. By identifyingcookies on a shared computing device, example methods, systems,apparatus and articles of manufacture disclosed herein determine themost likely user within the household that is using the computingdevice, and makes such identification in a manner that is non-intrusiveto the panelist member. Rather than inundating the panelist member withone or more prompts that force selection of their identity, examplemethods, apparatus, systems and articles of manufacture disclosed hereingenerate a list of known web-service cookies and associated useridentification information for each household member. The cookie havingthe most recent indication of modification, such as a timestamp,indicates one of many users in the household that is most likely usingthe computing device.

Although certain example methods, apparatus and articles of manufacturehave been described herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

What is claimed is:
 1. A method to identify a current user of acomputing device among a plurality of different users, the methodcomprising: identifying, by executing an instruction with a processor, amost recently used cookie based on a comparison of timestamps associatedwith a plurality of cookies; comparing, by executing an instruction withthe processor, an identifier of the most recently used cookie to acookie table, the cookie table associating cookies with the plurality ofdifferent users; and when the identifier of the most recently usedcookie is associated with one of the plurality of different users,associating, by executing an instruction with the processor, subsequentusage activity of the computing device with the one of the plurality ofdifferent users.
 2. The method as defined in claim 1, wherein when theidentifier of the most recently used cookie is not associated with anyof the plurality of different users, refraining from associating thesubsequent usage activity of the computing device with any of theplurality of different users.
 3. The method as defined in claim 1,wherein the subsequent usage activity of the computing device isbrowsing activity that is not associated with the most recently usedcookie.
 4. The method as defined in claim 1, wherein the associating ofthe subsequent usage activity occurs until a timeout period expires. 5.The method as defined in claim 1, wherein the most recently used cookieis associated with at least one of a social networking service, an emailservice, or a banking service.
 6. The method as defined in claim 1,wherein the plurality of cookies are from a first storage locationassociated with a first browser and a second storage location associatedwith a second browser.
 7. The method as defined in claim 1, wherein thecookie table is stored on the computing device.
 8. An apparatus toidentify a current user of a computing device among a plurality ofdifferent users, the apparatus comprising: a cookie manager to: identifya most recently used cookie based on a comparison of timestampsassociated with a plurality of cookies; and compare an identifier of themost recently used cookie to a cookie table, the cookie tableassociating cookies with the plurality of different users; and anactivity associator to, when the identifier of the most recently usedcookie is associated with one of the plurality of different users,associate subsequent usage activity of the computing device with the oneof the plurality of different users, at least one of the cookie manageror the activity associator implemented via a processor.
 9. The apparatusas defined in claim 8, wherein the activity associator is to, when theidentifier of the most recently used cookie is not associated with anyof the plurality of different users, refrain from associating thesubsequent usage activity of the computing device with any of theplurality of different users.
 10. The apparatus as defined in claim 8,wherein the subsequent usage activity of the computing device isbrowsing activity that is not associated with the most recently usedcookie.
 11. The apparatus as defined in claim 8, wherein the activityassociator is to associate the subsequent usage activity with the one ofthe plurality of different users until a timeout period expires.
 12. Theapparatus as defined in claim 8, wherein the most recently used cookieis associated with at least one of a social networking service, an emailservice, or a banking service.
 13. The apparatus as defined in claim 8,wherein the plurality of cookies are from a first storage locationassociated with a first browser and a second storage location associatedwith a second browser.
 14. The apparatus as defined in claim 8, whereinthe cookie table is stored on the computing device.
 15. A tangiblecomputer readable storage medium comprising instructions to identify acurrent user of a computing device among a plurality of different users,the instructions, when executed, cause a machine to at least: identify amost recently used cookie based on a comparison of timestamps associatedwith a plurality of cookies; compare an identifier of the most recentlyused cookie to a cookie table, the cookie table associating cookies withthe plurality of different users; and when the identifier of the mostrecently used cookie is associated with one of the plurality ofdifferent users, associate subsequent usage activity of the computingdevice with the one of the plurality of different users.
 16. The storagemedium as defined in claim 15, further including instructions that causethe machine to, when the identifier of the most recently used cookie isnot associated with any of the plurality of different users, refrainfrom associating the subsequent usage activity of the computing devicewith any of the plurality of different users.
 17. The storage medium asdefined in claim 15, wherein the subsequent usage activity of thecomputing device is browsing activity that is not associated with themost recently used cookie.
 18. The storage medium as defined in claim15, wherein the associating of the subsequent usage activity occursuntil a timeout period expires.
 19. The storage medium as defined inclaim 15, wherein the plurality of cookies are from a first storagelocation associated with a first browser and a second storage locationassociated with a second browser.
 20. The storage medium as defined inclaim 15, wherein the cookie table is stored on the computing device.